chore: rename bundle fields for consistency (no api change)#402
Merged
Conversation
akundaz
requested review from
0x416e746f6e,
SozinM,
avalonche and
karim-agha
as code owners
julio4
force-pushed
the
ash-xymzzupovxvt
branch
from
489d942 to
fe1ee27
Compare
Vui-Chee
added a commit
to okx/op-rbuilder
that referenced
this pull request
Feb 24, 2026
…tokio-tar * upstream/main: chore: rename bundle fields for consistency (no api change) (flashbots#402) Hotfix: pin nightly version to resolve str::as_str() regression (flashbots#401) update builder-playground usage for local devnet runs and testing (flashbots#395)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This way the field params match the external json-rpc params and we use
#[serde(rename_all = "camelCase")]at the struct level instead of manually renaming each field